Skip to content

Conversation

@fnesveda
Copy link
Member

We have started sending webhooks from the Apify platform through a predefined list of static IP addresses. This enables users (typically enterprise customers) who have the webhook destinations behind a firewall to whitelist these IP addresses in their firewall, and allow the delivery of these webhooks.

@fnesveda fnesveda added adhoc Ad-hoc unplanned task added during the sprint. t-core-services Issues with this label are in the ownership of the core services team. labels Feb 12, 2025
@fnesveda fnesveda added this to the 109th sprint - Platform team milestone Feb 12, 2025
@fnesveda fnesveda requested a review from seyhello February 12, 2025 15:36
@fnesveda fnesveda self-assigned this Feb 12, 2025
@fnesveda fnesveda requested a review from TC-MO as a code owner February 12, 2025 15:36
@fnesveda
Copy link
Member Author

@TC-MO I will merge this so that it's ready for all hands, but feel free to do any changes later 🙂

@fnesveda fnesveda merged commit 8ceb734 into master Feb 13, 2025
8 checks passed
@fnesveda fnesveda deleted the feature/route-webhooks-through-static-ips branch February 13, 2025 13:44
@TC-MO
Copy link
Contributor

TC-MO commented Feb 13, 2025

If you are okay with the changes suggested I'll make them later today :)

@fnesveda
Copy link
Member Author

I don't see any suggested changes 🤔

@TC-MO
Copy link
Contributor

TC-MO commented Feb 13, 2025

I did them as a comment in review not request changes about the admonition & etc

Comment on lines +168 to +181
## Source IP addresses

Webhooks are dispatched from servers with static IP addresses. If your webhook destination is protected behind a firewall, you can whitelist these IP addresses to allow Apify webhooks to be delivered:

- `3.215.64.207`
- `13.216.80.7`
- `13.216.180.86`
- `34.224.107.31`
- `34.236.208.85`
- `44.198.219.104`
- `44.207.71.44`
- `44.207.141.205`
- `52.4.20.206`
- `52.203.255.236`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest instead of separate heading at the end, to make it an admonition that would sit at the top of it (line 17?) this will be more visually appealing, and won't spread the text too much thanks to use of <details> tag. Below 2 screenshots with list collapsed and expanded

Suggested change
## Source IP addresses
Webhooks are dispatched from servers with static IP addresses. If your webhook destination is protected behind a firewall, you can whitelist these IP addresses to allow Apify webhooks to be delivered:
- `3.215.64.207`
- `13.216.80.7`
- `13.216.180.86`
- `34.224.107.31`
- `34.236.208.85`
- `44.198.219.104`
- `44.207.71.44`
- `44.207.141.205`
- `52.4.20.206`
- `52.203.255.236`
:::tip Webhook delivery
Webhooks are sent from servers that use static IP addresses. If your webhook destination is secured by a firewall, you can add the following IP addresses to your allow list to ensure Apify webhooks are delivered successfully.
<details>
<summary>IP list</summary>
- `3.215.64.207`
- `13.216.80.7`
- `13.216.180.86`
- `34.224.107.31`
- `34.236.208.85`
- `44.198.219.104`
- `44.207.71.44`
- `44.207.141.205`
- `52.4.20.206`
- `52.203.255.236`
</details>
:::

obraz
obraz

@fnesveda fnesveda added the validated Issues that are resolved and their solutions fulfill the acceptance criteria. label Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-core-services Issues with this label are in the ownership of the core services team. validated Issues that are resolved and their solutions fulfill the acceptance criteria.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants